The various tools expect the device node to be /dev/xen/evtchn -- this

makes it so that udev actually creates the device there

Signed-off-by: Jeremy Katz <katzj@redhat.com>

diff --git a/tools/examples/xen-backend.rules b/tools/examples/xen-backend.rules
index 21c6d8c8fc6cbdf2dcc3d763c77e98e99a18d1f4..2bd95d1a25e7e691a28b3ae5e99e4cb284c2b50c 100644 (file)
--- a/tools/examples/xen-backend.rules
+++ b/tools/examples/xen-backend.rules
@@ -4,3 +4,4 @@ SUBSYSTEM=="xen-backend", KERNEL=="vtpm*", RUN+="/etc/xen/scripts/vtpm $env{ACTI
 SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="online", RUN+="$env{script} online"
 SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="offline", RUN+="$env{script} offline"
 SUBSYSTEM=="xen-backend", ACTION=="remove", RUN+="/etc/xen/scripts/xen-hotplug-cleanup"
+KERNEL=="evtchn", NAME="xen/%k"